Skip to content

Standardize resource_id annotations to use bare values#737

Open
tconley1428 wants to merge 1 commit intomasterfrom
standardize-resource-id-prefix
Open

Standardize resource_id annotations to use bare values#737
tconley1428 wants to merge 1 commit intomasterfrom
standardize-resource-id-prefix

Conversation

@tconley1428
Copy link
Contributor

Summary

  • Remove prefix responsibility (workflow:, worker:) from proto annotations for resource_id fields
  • All resource_id annotations now use bare {resource_id}, making the SDK responsible for providing the fully-prefixed value
  • This standardizes the contract: previously activity request annotations used bare {resource_id} while workflow/worker request annotations used workflow:{resource_id} or worker:{resource_id}

Affected RPCs

  • ExecuteMultiOperation: workflow:{resource_id}{resource_id}
  • RespondWorkflowTaskCompleted: workflow:{resource_id}{resource_id}
  • RespondWorkflowTaskFailed: workflow:{resource_id}{resource_id}
  • RecordWorkerHeartbeat: worker:{resource_id}{resource_id}
  • FetchWorkerConfig: worker:{resource_id}{resource_id}
  • UpdateWorkerConfig: worker:{resource_id}{resource_id}

🤖 Generated with Claude Code

Remove prefix responsibility from proto annotations for resource_id
fields. Previously, some annotations used "workflow:{resource_id}" or
"worker:{resource_id}" while others used bare "{resource_id}". Now all
resource_id annotations use "{resource_id}", making the SDK responsible
for providing the fully-prefixed value in all cases.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@tconley1428 tconley1428 requested review from a team as code owners March 20, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants